home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19981211-19990422
/
000064_news@newsmaster….columbia.edu _Tue Dec 29 18:27:15 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1999-04-21
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id SAA19449
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 29 Dec 1998 18:27:15 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id SAA04049
for kermit.misc@watsun; Tue, 29 Dec 1998 18:27:14 -0500 (EST)
Path: news.columbia.edu!panix!logbridge.uoregon.edu!xmission!news.cc.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: telnet disconnects
Message-ID: <Oy5WwYEQKDJG@cc.usu.edu>
Date: 28 Dec 98 16:46:23 MDT
References: <765q0e$34l$1@samba.rahul.net> <768vg1$ni8$1@apakabar.cc.columbia.edu>
Organization: Utah State University
Lines: 25
Xref: news.columbia.edu comp.protocols.kermit.misc:9697
In article <768vg1$ni8$1@apakabar.cc.columbia.edu>, jaltman@watsun.cc.columbia.edu (Jeffrey Altman) writes:
> In article <768hci$j07$1@samba.rahul.net>, <dold@network.rahul.net> wrote:
> : Jeffrey Altman (jaltman@watsun.cc.columbia.edu) wrote:
> :
> : : Take a debug.log and when the connection breaks, look for ECONRESET,
> : : ENETRESET, ECONNABORTED, ENOTCONN, or "Unknown Error". These are the
> : : error types that will result in a disconnect.
> :
> : Hmmm. I don't see those keywords.
> : I've attached some lines at the end of the debug log from a C-Kermit
> : 6.0.192 running on Unixware.
> :
> : . mygetbuf errno=131
>
> I don't have access to Unixware. What does the errno.h file list
> error number 131 as on Unixware?
---------
Which version of UnixWare? Always important to know.
On UW 7.01, 131 is ECONNRESET connection reset by peer
Problems of this kind are frequent. Their cause is often another
station using the same IP number as yours. MS Windows machines can do this.
When they occur have a look in the ARP cache of the remote host or a router,
if possible.
Joe D.